Potential fix for code scanning alert no. 12: Incomplete string escaping or encoding #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Potential fix for https://github.com/SFARPak/ACode/security/code-scanning/12
To fix this problem, we need to ensure that all backslashes in the
pathare themselves escaped before escaping spaces. This is done by first replacing each single backslash (\) with a double backslash (\\). Then, replace each space () with a backslash followed by a space (\). These two replacements must be performed sequentially in that order—first escape all backslashes, then escape spaces—so there's no ambiguity and the output is parseable.Specifically, in the file
webview-ui/src/utils/path-mentions.tsat line 12, update theescapeSpacesfunction to first perform.replace(/\\/g, "\\\\")and then.replace(/ /g, "\\ "). No new imports are needed.Suggested fixes powered by Copilot Autofix. Review carefully before merging.